DRAKHYSYS WORKBENCH V4.8.7 — ONE INDEPENDENT ENTRANCE PER EXIT

You can create as many exits as the ARE format allows. Each exit can have its
own arrival entrance. Adding or updating the entrance for Exit B keeps Exit A's
entrance, name, coordinates and link.

HOW TO USE
1. Open START_TILESET_WORKBENCH.bat and AREA TRANSITIONS / ENTRANCES.
2. ADD ARE(S): load the source and destination areas.
3. On the source area, use NEW EXIT, choose the destination, draw its polygon,
   then FINISH / UPDATE EXIT. Repeat NEW EXIT for additional exits.
4. Switch to the destination area and load its map image.
5. Select the correct source/exit under Incoming exits targeting this area.
6. Click PLACE / MOVE ENTRANCE IN MAP, click the arrival point, then
   ADD / UPDATE ENTRANCE. SET ARRIVAL FOR THIS INCOMING EXIT does the same thing.
7. Choose another incoming exit and repeat. Its entrance is separate.
8. To move a previously saved arrival, select that incoming exit again, place
   its point and ADD / UPDATE ENTRANCE. It updates the same entrance.
9. EXPORT ALL LOADED AREAS writes both the source exit links and destination
   entrances. ADD / UPDATE commits changes in the editor; export saves to disk.

EXAMPLE
DR0001 / EXIT_A -> DR0003 / FROM_DR0001_EXIT_A
DR0001 / EXIT_B -> DR0003 / FROM_DR0001_EXIT_B
Moving EXIT_B's arrival does not move EXIT_A's arrival.

WHAT WAS FIXED
- Different incoming exits no longer overwrite the same START entrance.
- START and shared arrival names get a dedicated entrance when editing an exit.
- Returning to an exit finds its existing independent arrival for updates.
- Repeating ADD / UPDATE does not create duplicate entrances for the same exit.
- Refreshing dropdowns no longer silently selects an entrance for replacement.
- Creation uses unique names; a rename cannot overwrite another entrance.
- Renaming an entrance updates its existing links in loaded source areas.
- Editing an entrance directly by name does not rewire an unrelated selected exit.
- Same-area travel links survive refresh and export.
- Imported entrance record data is preserved during coordinate updates.

All existing entrance records are kept unless Delete selected entrance is used.
The entrance list includes older and unused entrances too. Selecting one there
allows direct editing; click the map and ADD / UPDATE ENTRANCE to save it.
The explicit LINK button remains available if you intentionally want two exits
to share a saved entrance. Moving one through its incoming exit makes it
independent again, so the other exit's arrival does not move.

There is no additional editor limit on exit/entrance count. Game file format
limits still apply. One travel region stores one destination entrance name.
Format reference: https://gibberlings3.github.io/iesdp/file_formats/ie_formats/are_v1.htm

TESTS
RUN_ENTRANCE_TESTS.bat runs the actual PySide6 transition editor regression tests.
RUN_SELF_TEST.bat runs the existing file-format checks.
V4_8_7_VALIDATION.json records the checks performed for this release.

This update changes the editor, not your supplied maps or chitin.key. Load your
existing ARE files and assign the arrival positions you want; no map remake is
needed. Game execution is not tested in this environment.

The V4.8.1 / V4.8.5 / V4.8.6 notes are historical. This file describes the current
one-entrance-per-exit workflow and supersedes their automatic-new-slot behavior.
